Release 10.1A: OpenEdge Data Management:
DataServer for ORACLE

Database triggers

Database triggers are code that an application associates with a database object and an action. For example, writing a record can cause code associated with that object or action to execute. The DataServer allows your applications to access both OpenEdge and ORACLE triggers. In an application that combines both OpenEdge and ORACLE triggers, the Progress 4GL trigger (CREATE, UPDATE, DELETE) executes first. As each OpenEdge trigger executes successfully, the DataServer passes the request to ORACLE, and the ORACLE trigger (INSERT, UPDATE, DELETE) executes. In the case of an ORACLE BEFORE trigger, the ORACLE trigger executes after the DataServer passes the request but before the insert, update, or delete occurs. When you use the Progress-to-ORACLE utility to convert an OpenEdge database to ORACLE, the utility does not convert Progress 4GL triggers into ORACLE triggers. The triggers remain in 4GL, and are part of the schema holder.